|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved legacy document.
|
|
3.
|
Justification for the specific reference:
|
|
|
The DPI functional model is based on packet forwarding function (PFF). The PFF may be e.g. a switching function in case of MPLS label switching routers (LSR) or Ethernet switches or bridges , or a forwarding/routing function in case of IPv4 [IETF RFC 791] and IPv6 [IETF RFC 2460] routers. See clause 7.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=791
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been approved in September 1981.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
This reference is a standards-track document and is currently in the "Proposed Standard" state. Current standards status of this document can be found at ftp://ftp.isi.edu/in-notes/std/std1.txt. Errata Exist. Updated by RFC 1349, RFC 6864, RFC 2474.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 791 is a fundamental component of the basic suite of internet protocols and standards. Updated by RFC 2474, RFC 6864, RFC 1349 , Errata exhist. Obsoletes RFC 760
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Cerf, V., "The Catenet Model for Internetworking", IEN 48, July 1978./
[2] Bolt Beranek and Newman, "Specification for the Interconnection of a Host and an IMP," BBN Technical Report 1822, Revised May 1978./
[3] Postel, J., "Internet Control Message Protocol - DARPA Internet Program Protocol Specification," RFC 792, September 1981./
[4] Shoch, J., "Inter-Network Naming, Addressing, and Routing," COMPCON, IEEE Computer Society, Fall 1978./
[5] Postel, J., "Address Mappings," RFC 796, September 1981./
[6] Shoch, J., "Packet Fragmentation in Inter-Network Protocols," Computer Networks, v. 3, n. 1, February 1979./
[7] Strazisar, V., "How to Build a Gateway", IEN 109, Bolt Beranek and Newman, August 1979./
[8] Postel, J., "Service Mappings," RFC 795, September 1981./
[9] Postel, J., "Assigned Numbers," RFC 790, September 1981.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
If the Study Group decides to make the reference to the RFC, the reference should always be made by RFC number (and not by other designations such as STD, BCP, etc.). References should not be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic".
|
|
